Remove critical-section requirement for no_std with atomics
#4322
+92
−15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daxpedda
force-pushed
the
no_std-atomics-critical-section
branch
from
91a301c to
3e22f1b
Compare
daxpedda
force-pushed
the
no_std-atomics-critical-section
branch
from
3e22f1b to
d83371e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When compiling with
no_stdandtarget-feature = "atomics", thelink_to!macro, used bywasm-bindgen-futures, requires an implementation ofcritical-sectionforonce_cell. This was a bit unfortunate, but #4277 was already too big so I left it for a follow-up.This PR adds a custom implementation for
LazyLock.